docs: #29 add UI specification #38
Conversation
There was a problem hiding this comment.
Since we agreed to include decade filtering, could we add the corresponding input and facet type to this PR as well? That keeps the UI specification and GraphQL contract aligned.
Suggested addition to AlbumSearchInput:
decades: [Int!]
Each value represents the first year of a decade, for example 1990 for the 1990s. The search result should also expose decadeFacets, similar to genreFacets, so the UI can show match counts for each decade.
|
I agree, this is added now! The schema now includes decades and decadeFacets, and I updated the data model to match as well. |
There was a problem hiding this comment.
Looks good. The UI specification now covers the M1 requirements clearly, and the decade filter is consistently reflected in the GraphQL schema and data model. The wireframes, empty state, paging behaviour, and accessibility considerations make the planned user experience easy to understand.
What this does
Adds the UI specification for #29 so reviewers can understand how the catalogue is intended to work before the client is connected to the backend.
What was done
docs/ui-specification.mdincludes:The specification is also linked from
docs/architecture.mdso it is easy to find.What was tested
Documentation only. Formatting checked with:
pnpm formatCloses #29.